im gonna convert the others too

im gonna convert the others too

I wonder if github has a way to make this org-level instead of each repo

I wonder if github has a way to make this org-level instead of each repo

there are some differences though, like eip712 doesn't care about your ape-config file or ape plugins, etc.
and ape-vyper may wonder about your vyper version + syntax

i just wish i can view / demo these before merging

Edit: OK I can on my fork / branch when viewing the files, so doing that now

I wonder if github has a way to make this org-level instead of each repo

there are some differences though, like eip712 doesn't care about your ape-config file or ape plugins, etc. and ape-vyper may wonder about your vyper version + syntax

yeah exactly, set an org-level, and then set specific ones for repos that don't match

im gonna convert the others too

I wonder if github has a way to make this org-level instead of each repo

yes there is!
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file#supported-file-types

yes there is! https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file#supported-file-types

OK, I followed those instructions and created https://github.com/ApeWorX/.github
Then, I removed any file here that was un-altered, FUNDING.yml, PULL_REQUEST_TEMPLATE.yml, and SECURITY.md guide, as all of those files are supported in the community repo thing

This gave me some other ideas for the .github repo

ApeWorX/.github#1